-
Notifications
You must be signed in to change notification settings - Fork 920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.4.0 #3268
Merged
Merged
Release 2.4.0 #3268
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Remove archived and inactive sites - Update URLs
Update list of sites
Remove "Who is Using" from Fractal docs
Add border-collapse rule to tables
USWDS - styles.scss Imports: Remove duplicate layout-grid import.
Prevent subcomponent type styles from overriding the primary component
Issue-3256: Prevent focus outline from being overridden.
Allow non-token values in theme color settings
Update dependencies
Promote better deprecation communication and compatibility
Update references to 2.4.0
Improve messaging about notification in notification
thisisdano
added
affects: banner
Affects: Compiling
Related to compiling Sass or JavaScript
Package: Footer
Package: Table
Affects: Documentation
Relates to documentation. Should this be in uswds-site?
labels
Dec 18, 2019
mejiaj
approved these changes
Dec 18, 2019
This was referenced Jan 15, 2020
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Affects: Compiling
Related to compiling Sass or JavaScript
Affects: Documentation
Relates to documentation. Should this be in uswds-site?
Package: Footer
Package: Table
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's new in USWDS 2.4.0
Allow non-token values in theme color settings. While USWDS promotes and encourages using our system tokens in theme color settings, agencies have a real need to occasionally use non-token colors. This includes instances where certain colors are mandated by law and cannot be easily changed. Now, teams can add non-token colors to theme color settings like
$theme-color-primary: #f00
. This new non-token value of'primary'
will apply anywhere the'primary'
token is used: functions, mixins, settings, and utilities. Using non-token values will throw a warning in the compile process, but this, like all compile warnings, can be disabled by setting$theme-show-compile-warnings: false
. (#3258)Handle deprecations more gracefully. Occasionally the design system will deprecate variables or functionality. Now we'll display a deprecation message in the terminal when compiling USWDS Sass to better communicate these changes. (This notification can be disabled in settings.) We're also improving backward compatibility by supporting deprecated variables, functions, and mixins throughout the major version cycle. This way, we can continue to improve how our code is structured while minimizing the effects of this restructuring on your projects. (#3261)
This is how the deprecation warning prints in the terminal:
Now components reliably respect their font settings. Setting values like
$theme-footer-font-family
should set the font face for the entire component, but some CSS specificity quirks were overriding these values in some instances. Now, setting a component's font face works as expected, with no secret overrides. (#3253)Bugfixes
border-collapse: collapse
rule to our tables to to fix a bug introduced when we upgraded our version of Normalize. Thanks for the heads up @maya! (Add border-collapse rule to tables #3250)